| Avoid slowing down the critical rendering path (avoidRenderBlocking) | The page has 1 blocking requests and 0 in body parser blocking (1 JavaScript and 0 CSS). | 90 |
| Description: The critical rendering path is what the browser needs to do to start rendering the page. Every file requested inside of the head element will postpone the rendering of the page, because the browser need to do the request. Avoid loading JavaScript synchronously inside of the head (you should not need JavaScript to render the page), request files from the same domain as the main document (to avoid DNS lookups) and inline CSS for really fast rendering and a short rendering path. |
| Offenders: https://apps.mypurecloud.com/messenger/newrelic/newrelic-agent.js |
| Don't scale images in the browser (avoidScalingImages) | The page has 5 images that are scaled more than 100 pixels. It would be better if those images are sent so the browser don't need to scale them. | 50 |
| Description: It's easy to scale images in the browser and make sure they look good in different devices, however that is bad for performance! Scaling images in the browser takes extra CPU time and will hurt performance on mobile. And the user will download extra kilobytes (sometimes megabytes) of data that could be avoided. Don't do that, make sure you create multiple version of the same image server-side and serve the appropriate one. |
| Offenders: https://images.vans.com/is/image/Vans/VN0A45EN_WHT_HERO...VN0A45EN_WHT_HERO https://images.vans.com/is/image/Vans/VN0A7Q5D_1NU_HERO?$PLP-IMAGE$ https://images.vans.com/is/image/Vans/VN000XG8_DJ7_HERO?$PLP-IMAGE$ https://images.vans.com/is/image/Vans/VN0A5KXM_W00_HERO?$PLP-IMAGE$ https://images.vans.com/is/image/Vans/VN0A3WMA_VNG_HERO?$PLP-IMAGE$ |
| Avoid using Google Tag Manager. (googleTagManager) | The page is using Google Tag Manager, this is a performance risk since non-tech users can add JavaScript to your page. | 0 |
| Description: Google Tag Manager makes it possible for non tech users to add scripts to your page that will downgrade performance. |
| Inline CSS for faster first render (inlineCss) | The page has both inline CSS and CSS requests even though it uses a HTTP/2-ish connection. If you have many users on slow connections, it can be better to only inline the CSS. Run your own tests and check the waterfall graph to see what happens. | 95 |
| Description: In the early days of the Internet, inlining CSS was one of the ugliest things you can do. That has changed if you want your page to start rendering fast for your user. Always inline the critical CSS when you use HTTP/1 and HTTP/2 (avoid doing CSS requests that block rendering) and lazy load and cache the rest of the CSS. It is a little more complicated when using HTTP/2. Does your server support HTTP push? Then maybe that can help. Do you have a lot of users on a slow connection and are serving large chunks of HTML? Then it could be better to use the inline technique, becasue some servers always prioritize HTML content over CSS so the user needs to download the HTML first, before the CSS is downloaded. |
| Avoid CPU Long Tasks (longTasks) | The page has 49 CPU long tasks with the total of 8.218 s. The total blocking time is 5.729 s and 1 long task before first contentful paint with total time of 89 ms. However the CPU Long Task is depending on the computer/phones actual CPU speed, so you should measure this on the same type of the device that your user is using. Use Geckoprofiler for Firefox or Chromes tracelog to debug your long tasks. | 0 |
| Description: Long CPU tasks locks the thread. To the user this is commonly visible as a "locked up" page where the browser is unable to respond to user input; this is a major source of bad user experience on the web today. However the CPU Long Task is depending on the computer/phones actual CPU speed, so you should measure this on the same type of the device that your user is using. To debug you should use the Chrome timeline log and drag/drop it into devtools or use Firefox Geckoprofiler. |
| Offenders: selfselfselfselfselfselfselfselfselfselfselfselfmultiple-contextsmultiple-contextsselfselfselfselfmultiple-contextsselfselfselfcross-origin-descendantcross-origin-descendantselfselfselfselfselfselfselfselfmultiple-contextsselfcross-origin-descendantselfselfselfselfselfselfselfselfselfselfselfselfmultiple-contextsself |
| Avoid Frontend single point of failures (spof) | The page has 1 request inside of the head that can cause a SPOF (single point of failure). Load them asynchronously or move them outside of the document head. | 90 |
| Description: A page can be stopped from loading in the browser if a single JavaScript, CSS, and in some cases a font, couldn't be fetched or is loading really slowly (the white screen of death). That is a scenario you really want to avoid. Never load 3rd-party components synchronously inside of the head tag. |
| Offenders: https://fonts.googleapis.com/css?family=Barlow:200,400,700 |
| Avoid doing redirects (assetsRedirects) | The page has 1 redirect. 1 request are from other domains, it could be 3rd-party assets doing unnecessary redirects. :( | 90 |
| Description: A redirect is one extra step for the user to download the asset. Avoid that if you want to be fast. Redirects are even more of a showstopper on mobile. |
| Offenders: https://10192411.fls.doubleclick.net/activityi;src=10192411;type=visit0;cat=30da...shoe-pvn000eyew00 |
| Avoid extra requests by setting cache headers (cacheHeaders) | The page has 31 requests that are missing a cache time. Configure a cache time so the browser doesn't need to download them every time. It will save 6.5 kB the next access. | 0 |
| Description: The easiest way to make your page fast is to avoid doing requests to the server. Setting a cache header on your server response will tell the browser that it doesn't need to download the asset again during the configured cache time! Always try to set a cache time if the content doesn't change for every request. |
| Offenders: https://www.facebook.com/tr/....facebook.com/tr/ https://www.vans.ca/api/products/v1/products/VN000EYEW00/details?locale=en-ca https://www.vans.ca/api/products/v2/products/VN000EYEW00/inventory?locale=en-ca https://www.vans.ca/api/wishlists/v2/favorites https://www.vans.ca/api/products/v1/products/reviews/configuration...ews/configuration https://www.vans.ca/api/products/v1/products/VN000EYEW00/reviews?reviewLocale=en_CA&sort=Newest https://www.vans.ca/content/publish/caas/v1/commercepage/vans-en-ca/product/VN000EYEW00 https://f.monetate.net/trk/4/s/a-1c6f575e/p/vans.ca-1.5/919696133-3...a-1.5/919696133-3 https://www.facebook.com/tr/....facebook.com/tr/ https://vfcorp.d1.sc.omtrdc.net/b/ss/vfcvanscaprod/1/JS-2.13.1/s5769263783158....1/s5769263783158 https://nova.collect.igodigital.com/c2/514010235/track_page_view...5/track_page_view https://googleads.g.doubleclick.net/pagead/viewthroughconversion/849976899/...ersion/849976899/ https://10192411.fls.doubleclick.net/activityi;src=10192411;type=visit0;cat=30da...shoe-pvn000eyew00 https://10192411.fls.doubleclick.net/activityi;dc_pre=CMSsw4Sp5P4CFUvlhwodn0wDXw...shoe-pvn000eyew00 https://apps.mypurecloud.com/genesys-bootstrap/genesys.min.js https://c.contentsquare.net/pageview...uare.net/pageview https://www.facebook.com/tr/....facebook.com/tr/ https://p.brsrvr.com/pix.gif...rsrvr.com/pix.gif https://bat.bing.com/action/0...bing.com/action/0 https://adservice.google.com/ddm/fls/z/dc_pre=CMSsw4Sp5P4CFUvlhwodn0wDXw;src=101...shoe-pvn000eyew00 https://www.google.com/pagead/1p-user-list/849976899/...r-list/849976899/ https://www.google.com.co/pagead/1p-user-list/849976899/...r-list/849976899/ https://apps.mypurecloud.com/messenger/messenger.html https://apps.mypurecloud.com/messenger/newrelic/newrelic-agent.js https://apps.mypurecloud.com/cxbus/cxbus.min.js https://apps.mypurecloud.com/messenger/messagingMiddleware.min.js https://apps.mypurecloud.com/messenger/defaultVendors.min.js https://apps.mypurecloud.com/messenger/vendors.min.js https://apps.mypurecloud.com/messenger/main.min.js https://apps.mypurecloud.com/messenger/engage.min.js https://bam-cell.nr-data.net/1/7a5b0de38e....net/1/7a5b0de38e |
| Long cache headers is good (cacheHeadersLong) | The page has 19 requests that have a shorter cache time than 30 days (but still a cache time). | 81 |
| Description: Setting a cache header is good. Setting a long cache header (at least 30 days) is even better beacause then it will stay long in the browser cache. But what do you do if that asset change? Rename it and the browser will pick up the new version. |
| Offenders: https://images.vans.com/is/image/Vans/VN000EYE_W00_is...s/VN000EYE_W00_is https://images.vans.com/is/image/Vans/VN000EYE_W00_HERO...VN000EYE_W00_HERO https://images.vans.com/is/image/Vans/VN000EYE_W00_ALT1...VN000EYE_W00_ALT1 https://images.vans.com/is/image/Vans/VN000EYE_W00_ALT2...VN000EYE_W00_ALT2 https://images.vans.com/is/image/Vans/VN000EYE_W00_HERO...VN000EYE_W00_HERO https://images.vans.com/is/image/Vans/VN000EYE_W00_ALT1...VN000EYE_W00_ALT1 https://images.vans.com/is/image/Vans/VN000EYE_W00_ALT2...VN000EYE_W00_ALT2 https://images.vans.com/is/image/Vans/VN000EYE_BKA_HERO...VN000EYE_BKA_HERO https://images.vans.com/is/image/Vans/VN000EYE_CHR_HERO...VN000EYE_CHR_HERO https://images.vans.com/is/image/Vans/VN000EYE_NVY_HERO...VN000EYE_NVY_HERO https://images.vans.com/is/image/Vans/VN000EYE_BLK_HERO...VN000EYE_BLK_HERO https://images.vans.com/is/image/Vans/VN0A4U38_IYP_HERO...VN0A4U38_IYP_HERO https://images.vans.com/is/image/Vans/VN0A4BV3_TC3_HERO...VN0A4BV3_TC3_HERO https://images.vans.com/is/image/Vans/VN0A38F7_ODJ_HERO...VN0A38F7_ODJ_HERO https://images.vans.com/is/image/Vans/placeholder?$PLP-IMAGE$ https://images.vans.com/is/image/Vans/VN0A45EN_WHT_HERO...VN0A45EN_WHT_HERO https://images.vans.com/is/image/Vans/VN0A7Q5D_1NU_HERO?$PLP-IMAGE$ https://images.vans.com/is/image/Vans/VN0A5KXM_W00_HERO?$PLP-IMAGE$ https://images.vans.com/is/image/Vans/VN0A3WMA_VNG_HERO?$PLP-IMAGE$ |
| Always compress text content (compressAssets) | The page has 1 request that are served uncompressed. You could save a lot of bytes by sending them compressed instead. | 90 |
| Description: In the early days of the Internet there were browsers that didn't support compressing (gzipping) text content. They do now. Make sure you compress HTML, JSON, JavaScript, CSS and SVG. It will save bytes for the user; making the page load faster and use less bandwith. |
| Offenders: |
| Total JavaScript size shouldn't be too big (javascriptSize) | The total JavaScript transfer size is 4.9 kB and the uncompressed size is 1.4 MB. This is totally crazy! There is really room for improvement here. | 50 |
| Description: A lot of JavaScript often means you are downloading more than you need. How complex is the page and what can the user do on the page? Do you use multiple JavaScript frameworks? |
| Offenders: |
| Don't use private headers on static content (privateAssets) | The page has 3 requests with private headers. Make sure that the assets really should be private and only used by one user. Otherwise, make it cacheable for everyone. | 70 |
| Description: If you set private headers on content, that means that the content are specific for that user. Static content should be able to be cached and used by everyone. Avoid setting the cache header to private. |
| Offenders: https://vfcorp.d1.sc.omtrdc.net/b/ss/vfcvanscaprod/1/JS-2.13.1/s5769263783158....1/s5769263783158 https://nova.collect.igodigital.com/c2/514010235/track_page_view...5/track_page_view https://10192411.fls.doubleclick.net/activityi;dc_pre=CMSsw4Sp5P4CFUvlhwodn0wDXw...shoe-pvn000eyew00 |
0 s
0.5 sFirst Visual Change 470 ms
0.6 s
0.8 s
0.9 s
1 s
1.3 s
1.4 s
1.5 sFirst Contentful Paint 1.474 sCPU Long Task duration 158 ms
1.6 s
1.7 s
1.8 sCPU Long Task duration 435 msLCP <> 1.766 s
1.9 s
2 sVisual Complete 85% 1.949 s
2.1 s
2.2 sDOM Content Loaded Time 2.102 sCPU Long Task duration 77 ms
2.4 sAA - CDN Loaded 2.373 s
2.7 sCPU Long Task duration 495 ms
3.4 sCPU Long Task duration 97 msVisual Complete 95% 3.395 s
3.6 sLast Visual Change 3.529 sVisual Complete 99% 3.529 sCPU Long Task duration 211 ms
